Apple Reference & Presen…rary 8 (Internal Edition)/Apple R&P Lib Internal v8.0.iso/3-Presentations/Apple Computer Inc./Industry Competition/ROMs/Software/OfficeVision pt. 1

Text File | 1990-06-24 | 27.1 KB | 555 lines | [TEXT/GEOL]

Apple Confidential / Need to Know

By:  Michael Bobrowicz, Dave Garr, Michael Mace.



Effect on Customers

IBM did an excellent job of creating some “top line” perceptions in the minds
of customers:
• That IBM customers will see the same interface regardless of application or
desktop device.
• That developer support for OfficeVision is overwhelming.
• That the only way customers can take advantage of this new functionality is
by putting IBM hardware on every desk.
But the reality is significantly different from the perceptions.

Who will control the desktop?  Even though the new functionality of
OfficeVision is delivered first on PCs and LANs, IBM has positioned this as an
MIS/mainframe-centered announcement.  The role of the personal computer, which
IBM now calls the Programmable Workstation, is to serve as an entry point to
host-resident data and applications.  IBM is asking its customers to turn over
the keys to the desktop in order to get at their host-based data.  While this
will appeal to those customers who “don’t buy it if it doesn’t say IBM,” other
customers may feel threatened.

It is not clear if IBM will actually try to physically lock competitive PCs out
of OfficeVision, or just threaten to do it (a typical FUD tactic).  We think
the latter is much more likely.  The situation with OS/2 Extended Edition is a
good example.  IBM still won’t guarantee that third party PCs (like Compaq) can
run Extended Edition, the operating system on which OfficeVision is based.  In
reality, clones can currently run Extended Edition, but IBM won’t say so.  IBM
is also holding open the possibility that future versions of EE will be somehow
connected to the PS/2’s Micro Channel architecture, precluding clones from the
desktop unless they pay IBM royalties.  This is the sort of uncertainty
customers will face when they consider moving to IBM’s solution.

Migration costs.  Customers who buy into Office Vision and Extended Edition 1.2
will be asked to replace their current LAN operating system,  LAN or
minicomputer based office information applications and hardware, and third
party communications cards and software.  All will be replaced with proprietary
IBM hardware and software.  This would mean a very disruptive migration for
some firms.

Broken promises in SAA.  Although IBM touts OfficeVision as a fulfillment of
SAA, the product also violates some of the promises IBM made when SAA was
announced.  IBM said that Common User Access, the interface specification in
SAA, would guarantee customers the same user interface on its terminals and
PCs, regardless of the application, processor, etc.  This is no longer the
case, because OfficeVision does not work the same on terminals as it does on
PCs.  In addition, IBM’s other software announced alongside OfficeVision uses
other interfaces, some of them very different from OfficeVision.  Instead of
simplifying its interface situation, IBM has actually complicated it further.

The bottom line is that either IBM will be attempting to force its customers to
move away from terminals, an expensive prospect, or IBM will not be delivering
a truly consistent interface across its products—invalidating its original SAA
promises.

Developer issues.  The OfficeVision developers which were featured in the IBM
announcement are obvisouly getting advanced looks at the OfficeVision
programming interfaces.  In the PC world this means Microsoft and Lotus have a
head start.  In addition, Microsoft’s claims that its operating system
operation and its application operation are thoroughly separated is undermined
by its cooperation with IBM on OfficeVision.  This sort of pseudo “insider
trading” has the potential to upset a lot of developers.


Long-term effect on Apple

It’s too early to be sure how OfficeVision will affect Apple long term.  We
won’t have any firm ideas until we actually see the product.  In the short term
we believe that some loyal Fortune 1000 customers may postpone purchases
pending evaluation of the released product.

Apple probably will be able to connect Macintosh workgroups to OfficeVision
services, if compatibility with OV becomes a check-off item for customers.  In
fact, in order to lock Apple out of OfficeVision, IBM would have to violate
some of its own SAA guidelines for programming and communications interfaces.
So either Apple can get in easily, or SAA—the centerpiece of IBM’s computing
strategy— is invalid.


3.  IBM’s Approach vs. Apple’s

Superficially, the vision of corporate computing now being articulated by IBM
is similar to Apple's:  make the PC a window to transparently access the
company's computing resources.  However, there are several major differences
between IBM's approach and Apple's.

IBM’s approach is sometimes referred to as “big, blue, bolted, and belated.”
(“Big” because it requires so much hardware; “blue” because IBM connects mostly
just to IBM, “bolted” because elements tend to be stuck together incrementally
instead of crafted as a whole, and “belated” because products with similar
functionality were available from other companies long ago.)  Here’s how
Apple’s approach compares to IBM’s:


Focus:  User vs. Mainframe

Apple’s design focus is on empowering the person using the computer.  Because
Apple makes only personal computers, it can pursue that approach without
contradictions or hidden agendas.  IBM, on the other hand, has a massive
mainframe business to protect.  This forces it to adapt its PC products to the
needs of the mainframe.  In fact, IBM officials said after the OV announcement
that one of its main purposes was to drive up the use of mainframes.

Customer Impact:  Disruption vs. Compatibility

For many IBM customers a commitment to OV will mean abandoning substantial
investments made over the years on applications and data.  As an example, to
support OV Mail, customers will have to move away from popular systems such as
PROFS.

In contrast Apple presents a track record of user interface consistency, of
application compatibility between older and new systems, and of system
upgradability over the years.  A Mac customer can still use the 1984 Multiplan
spreadsheet designed for the Mac 128 on a Mac IIx in 1989; or can transfer the
spreadsheet data into a more powerful application.


Availability:  Promises vs. Reality

As mentioned earlier, OV will not become a widespread reality across all main
IBM systems for quite some time.  One IBM customer—a member of the OV Advisory
Council and, therefore, with a head start in SAA implementation—was quoted by
the press as ready to seriously consider implementing OV three years from now!

Many functions equivalent to OV are available on the Macintosh today.  As an
example, Mac customers have today the choice among at least six E-Mail systems
and three calendaring applications from third parties.


Price:  High Cost vs. Added Value

While the prices for the OV software  on the PC or the PS/2 are relatively
reasonable, the price for the minimal hardware configurations to run this
software is practically outside of the normal personal computer price range.
According to the Gartner Group, the price is at least $12,000 for a PS-based
client workstation and $18,000 for a PS-based server.

Macintosh customers can choose within a range spanning from the Macintosh Plus
to the Macintosh IIx.  And, for networking applications, sophisticated
functionality is made available to smaller Macintoshes through the distribution
of communications functions over AppleTalk; as an example, a Mac II with a
TokenTalk NB Card can distribute MacAPPC sessions to Mac Plus and SEs connected
to this Mac II via LocalTalk cabling.


Openness:  Single Vendor vs. Multivendor

IBM is working hard at getting as many third party software vendors as possible
to support OV. So far most of the companies on the OV bandwagon are mainframe
software vendors.  Though it is expected that other computers will be able to
connect to OV systems (Apple will connect the Macintosh when OV becomes
dominant within the IBM environment), IBM is definitely turning the page of the
era when MS-DOS could run on a wide range of platforms.

For the Macintosh, Apple has clearly stated a multivendor strategy.  For
networking, while Apple continues to develop AppleTalk as an integral part of
the Macintosh architecture, the company works hard at enabling the execution of
the AppleTalk protocols on other systems.  In addition, Apple’s strategy
clearly defines the integration of the Macintosh into four dominant computing
environments (i.e. Digital, IBM, OSI, TCP/IP) as top priority.


User Interface:  Contradictions vs. Consistency

One of the main objectives of SAA is to enable various IBM systems to
interoperate by reducing the number of hardware/software combinations through
the selection of a minimal set of specifications for each critical aspect of a
computing system (e.g. data base system, programming language, communication
interface, user interface, etc.).  With the announcement of OV—which is
supposed to strictly follow the SAA rules—IBM has introduced at least four new
user interfaces.

In contrast, Apple’s approach shines by its simplicity and its elegance.
Apple’s user interface has evolved since 1984 with a remarkable consistency.
This is the result of careful choices, of crafted integration, and of
persistent evangelism.  While IBM tries to narrow down by leaps and bounces,
Apple expands through regular and meaningful increments.


Specifications:  Moving Targets vs. Enduring Approach

This report describes how IBM is changing the Common User Access (CUA)
specifications—an integral part of SAA—to accommodate new user interfaces, and
IBM’s decision to declare “dumb” terminals second class citizens (before
becoming dinosaurs, then extinct).  This is an interesting approach: change the
specifications to accommodate new products rather than design new products
according to the specs.  How do IBM customers and third party friends find
their way through such moving targets?  How can they be sure that the targets
are not going to move again?

On the Macintosh side the contrast is again striking.  The persistence of the
original vision, the intense focus on the user, and the perpetual search for
elegance are key factors that have guided the evolution of the Macintosh
specifications since day one.  The contents of the specifications in Inside
Macintosh have rarely changed; they have been extended instead.  The result of
this enduring approach is, year after year, an increasing number of innovative
applications which share a consistent user interface but which, at the same
time, exploit the increasing capabilities of the Macintosh.


4.  OfficeVision Q & A

Q: What is Apple's overall response to Office Vision?

A: We are very interested in IBM's OfficeVision and will watch it closely as
IBM continues to work on it. Of course, providing a consistent personal
computing environment for the user has always been a foundation of Macintosh,
and Apple has provided this to our users since the Macintosh was first
introduced.

As was discussed in the previous section, IBM’s approach bears some superficial
similarities to Apple’s, but the underlying goals are very different.  IBM’s
mainframe-centered approach is fundamentally different from Apple’s PC-centered
vision.  This diagram illustrates the contrast:



Other Questions

Q:  If I want to run OfficeVision, am I required to buy only IBM PCs?

A:  Since OfficeVision is not yet a real product, it's difficult to say
anything definite about it.  However, Gartner Group, an independent PC analysis
firm, has studied OfficeVision and says that third party PCs will be able to
connect into it.  Gartner believes that IBM will try to make compatibility
sound uncertain, in order to encourage customers to buy PS/2s.  Specifically,
Gartner says Macintosh is not locked out of OfficeVision.


Q:  How does Macintosh software compare to OfficeVision?

A:  Third-party Macintosh developers already offer many of the features
promised in the future for OfficeVision—things like calendaring, electronic
mail, and document storage and retrieval.  Other Macintosh products, like the
multiuser document editor Markup, give workgroup features not found in
OfficeVision.


Q:  Isn't OfficeVision the only way to get one user interface throughout a
corporate computing environment?

A:  IBM's products will not all share one interface even after OfficeVision
ships.  In fact, at the May announcements, IBM announced four different
interfaces:  OfficeVision itself, the new version of OS/2 Standard Edition, the
IBM Data Interpretation System (Metaphor), and IBM Executive Decisions/VM.  If
you count the Next Step interface adopted for IBM's Unix products, the company
plans to sell at least five different graphical interfaces.


Q:  How does the cost of OfficeVision compare to Macintosh?

A:  Macintosh is less expensive per user.  According to Gartner Group, a
Macintosh IICX configured for network use costs $8,311, while its IBM
equivalent set up for OfficeVision, an IBM PS/2 Model 70, costs $12,956.  Much
of that difference is due to memory costs; OfficeVision requires eight or more
megabytes of RAM in order to function.


Q:  Now that IBM is giving me a good graphical interface, why should I buy
Macintosh?

A:  Four reasons:
    1.  Apple has it now.
    2.  Macintosh uses one consistent interface.  IBM offers at least four.
    3.  We think the Macintosh interface is significantly better than the ones
IBM is developing.
    4.  Macintosh is a lot more than a pretty interface.  It is, overall, the
best personal computer in the world.  People buy it because of everything it
does for them, not just for the way the screen looks.







OS/2 EXTENDED EDITION


Features & Evaluation

IBM announced a number of enhancements and new feature additions to Extended
Edition, its proprietary version of OS/2.   The new Extended Edition 1.2 has a
lot more workgroup communications and database functionality than the current
version, 1.1.

The specifics of the Database Manager and Communications Manager enhancements
are discussed below.  The intent of the announcement is clear:  add relational
database connectivity between any IBM computers, a crucial component of IBM’s
strategy.  Such capability is essential to what we believe is IBM’s ultimate
intention:  to turn mainframes into corporate wide servers.  Without some sort
of “any to any” database capability, IBM would be unable to do this.

IBM has essentially outlined a strategy and (provided the initial pieces) where
any client can access any database server regardless of the processor used by
the server, or its location (either physical or logical).  APPC (Advanced Peer
to Peer Communications) is the programming enabler for this connection while
Token Ring or SDLC (Synchronous Data Link Control) is used for transport.

Evaluation.  In the LAN environment, IBM has not delivered startling
functionality.  Any number of LAN OS vendors and third parties offer the same
sort of features.  What IBM has done is combine all of these elements into a
single system.  While the individual components lose some luster in head to
head comparisons, the total solution is impressive—assuming IBM delivers as
promised.


EE Database Manager Enhancements

Remote Data Services:  Allows a PC to function as a database requestor and/or
database server workstation.  Remote Data Services will allow multiple
workstations to access a common database, or a single workstation to access
geographically distributed databases.  The location of the server database
should be transparent to the requesting user (or application).  Using remote
Data Services, multiple application programs can access a single data base at
the same time.  Also, a single application can access multiple databases
serially.  Remote Data Services can be used in an IBM Token Ring, IBM PC
Network LAN or Ethernet environment.  Any workstation using the Remote Data
Services, as server or requestor, will use the APPC programming interface in
the Communications Manager.

DOS Database Requestor:  Allows a DOS workstation to access an OS/2 Extended
Edition Database Manager database.  The DOS Requestor supports the SQL
(Structured Query Language) application programming interface in the DOS
environment.  It also supports a subset of the Database Services Environment
Utility.  But there are two important caveats:  First, applications running on
the DOS Database Requestor must be precompiled on an OS/2 Extended Edition
database manager workstation and then compiled as a DOS application.  Then the
application can be transferred to the DOS workstation for execution.  Second,
the DOS Database Requestor is not provided with a graphical user interface.

Query Manager Callable Interface:  This lets an application call EE’s database
Query Manager.

Business Graphics Interface:  Customers can use this to install and use a
vendor business graphics program that has been written to this interface.  This
means report data that was accessed by an SQL query can be displayed
graphically.

User profile management and SQL Grant/Revoke statements  are security measures
designed to help control user access to a database and the tables within a
database.

COBOL, Pascal, and FORTRAN support  allow embedded SQL statements to be
included in programs written in COBOL/2, Pascal/2 and IBM FORTRAN/2.  SQL
statements may be embedded into application programs allowing the programs to
interface with the Database Manager and access the data in the database.

Query Manager operation as a Presentation Manager application.  This means the
Query Manager can utilize Presentation Manager controls, graphics, icons and
windowing capabilities.

Operational Status Tool provides a snapshot of information about current
database activity.  Among the information provided is information about where
the databases are located, names and user detail information on each user
connected to the database.


EE Communication Manager Enhancements

SNA Gateway support increased.  It now supports 256 workstations, up from 32.
The gateway allows access to a System/370 host computer by users connected to
the gateway via an IBM Token Ring, IBM PC Network LAN, SDLC switched link, or
an X.25 network.  The personal computer acting as the gateway appears to the
host as a single physical unit with up to 254 logical units, which can be
shared among the workstations.  The workstation appears to the user as if it
were directly attached to the host.

3270 emulation improved.  IBM added 3270 host directed support, 3270 graphics
support enabling and presentation space print (3270 local copy only).  Multiple
printer sessions are supported and the workstation can be standalone or
connected to a gateway.  In addition, 3270 graphics support works with the
GDDM-OS/2 Link, which is a program that adds graphics support to the 3270
emulator.  This allows workstations to function as GDDM mainframe graphics
terminals.  GDDM pictures can be printed or plotted or saved to a Presentation
Manager metafile.

The 3270 and ASCII emulators now use the Presentation Manager and its windowing
facilities.  Each logical terminal will appear in a separate window that can be
individually manipulated by the user.  The functionality includes starting,
stopping, moving and sizing windows.  The 3270 emulator can also use Mark, Cut,
Copy, Paste and Undo.  The ASCII emulator has support for Mark and Copy.  Users
can transfer information between Communication Manager windows and other
application windows that support clipboard.

Ethernet support.  Communication Manager now supports Ethernet DIX version 2.0
and IEEE 802.3 LANs.  The Network Driver Interface Specification (NDIS) is used
to provide this support.

X.25 support.  Called OS/2 Extended Edition Version 1.2 X.25 Packet Switched
Data Network (PSDN), it allows Model 50Z or higher machines to attach to and
communicate with other systems or host computers having appropriate X.25
support.

AS/400 communications has been improved to allow IBM Token Ring, X.25,
twinaxial, and remote connection via the IBM 5394 Remote Control Unit links (in
addition to existing SDLC links).  All these use LU (Logical Unit) 6.2
protocols.  A 5250 workstation feature was announced that provides the
functions of up to five display/printer sessions.

LAN Requestor supports HPFS.  The LAN Requestor in Extended Edition 1.2 will
work with the High Performance File System of the new OS/2 Standard Edition.
In addition to performance improvements, this system will manage large disk
media.

LAN Server, LAN Manager integration improved.  IBM improved the
interoperability between LAN Server and Microsoft’s LAN Manager by announcing
support for an additional 83 LAN Manager APIs, including Named Pipes and Mail
Slots.  Properly-written OS/2 programs should be able to access the Microsoft
and IBM LAN servers interchangably.


OS/2 EE Analysis

EE 1.2 offers no price/performance or functionality breakthroughs relative to
competitive systems.  IBM has done two things with this announcement:
(1) Articulated its vision of a distributed/cooperative environment at the
desktop level; and
(2) Provided much of the protocol infrastructure needed to implement this
vision.

We believe Macintosh competes well in terms of protocols supported.  In fact,
Macintosh offers a superior experience by accessing those protocols smoothly.
Still, there are some features IBM will offer that are not yet available in
Apple labeled products, and IBM has fixed some glaring flaws in Extended
Edition.


Flaws in EE that IBM fixed

Cut and paste added to 3270, ASCII emulation.  This is done via the
Presentation Manager and its windowing facilities.  IBM customers will be able
to cut, copy, paste, etc. in much the same way Apple customers do.

IBM also improved the graphics capability of its 3270 emulation products by
adding multiple printer session support and the GDDM-OS/2 link.  Such host
based graphics support is not included in Apple’s Coax/twinax NB (NuBus) card.
We think IBM is likely to use that to help differentiate its product from
Apple’s.

LAN Server, LAN Manager interoperability improved.  This eliminates a major
source of customer concern.  IBM’s LAN operating system and Microsoft’s LAN
operating system will now be able to work together with a minimum of
difficulty.  For example, a customer on a LAN Server network (which is IBM’s
LAN operating system) will be able to print to a printer on a LAN Manager
network (this is Microsoft’s product).  Before the announcement, this was not
possible.  Macintosh connects to these two environments via third party support
from Novell (Netware for the Mac, which is shipping now) and 3Com (3+ Open
scheduled to ship in early ‘90).


IBM is Seeking the Lead in Distributed Computing

IBM has articulated its vision.  We think the biggest difference between EE 1.2
and Macintosh is directional:  IBM has more fully articulated its vision of
distributed computing.  IBM’s vision is based on relational database (which
includes the Database Manager of EE 1.2) and DIA/DCA (Document Interchange
Architecture/ Document Content Architecture).

How IBM’s vision works.  In an oversimplified explanation, IBM’s vision
consists of DB2 (database) running on mainframes that act as corporate or
departmental data repositories.  These repositories are accessed by standalone
or networked PCs running Extended Edition.  How that information is structured
(page format, image storage, graphics definitions, etc.), is defined by the
various object definitions within DIA/DCA.

So for example,  a customer could write a report whose graphics reside in one
computer (mainframe, PC, or midrange wouldn’t matter), the text in another, and
scanned images in a third.  Using Extended Edition 1.2 and DB2, all the
different objects could be sent to a single PC and turned into one report
there.  (In theory, some of the computational load could also be offset to
upstream systems, but in practice we think they will be used mostly for data
storage and retrieval.)

IBM’s products aren’t ready, but its direction is clear.  Customers can’t do
this today because IBM has yet to deliver all the parts, but some essential
components are available:  LANs, Database Manager, and DB2.  And IBM has made
clear to its customers how it intends to proceed, which means IBM’s customers
can begin planning.  Apple offers connectivity into these IBM products as well
as LAN capability (AppleTalk), and database access (CL/1) of its own.  But
Apple has not yet completely articulated how it intends to distribute
processing, database access, etc. across its environment.


Q & A

Q:  How do IBM’s connectivity products stack up against Apple’s?

A:  Apple’s products are much stronger in multivendor connectivity.  The
features Apple has added to Macintosh work to extend the reach and
functionality of the computer smoothly, which is a contrast to IBM’s sometimes
disruptive approach.  We also think Apple systems will cost less, when fully
configured, than IBM systems set up to do the same thing.  IBM’s greatest
strength is in connectivity to other IBM products.  In that area, IBM currently
gives a larger feature set than Apple does.






OS/2 STANDARD EDITION


Features & Evaluation

IBM announced several enhancements that will be included in OS/2 version 1.2,
which is scheduled to ship September 29, 1989.  The most important of these is
a new graphical file manager.  IBM also promised to add some programmer tools,
a new file system, and better driver support.  The changes will remove some of
the most glaring weaknesses of OS/2.  We think Macintosh will remain a superior
environment, but several of the easiest "knockoffs" against OS/2 will
disappear.

The file manager.  IBM said two new graphical file management tools would be
added to PM:  the Desktop Manager and the File Manager.  We aren't sure what
the difference is between them, but together they appear to give PM an iconic
file management system.  IBM's documents promise iconic representations of
files and direct manipulation of them using the mouse, but it is not clear
exactly how it will all work.  During the announcement, IBM showed screen shots
of printer and document icons, but that was apparently OfficeVision.  It's not
clear which features will also be included in standard OS/2.

New file system.  IBM said it will add a new High Performance File System which
can access up to two gigabytes of disk space, gives file names up to 255
characters, and is reportedly much faster.  Disks formatted using the new
system cannot be read by computers running DOS.  However, DOS programs working
in OS/2's Compatibility Box will be able to read the new structure.

Programming tools.  The Dialog Manager is a tool designed to aid the creation
of simple "form fill" applications.  It provides a user interface shell into
which a few simple interface elements like text entry boxes and push buttons
can be added.  The program does not support the system clipboard, and does not
allow the programmer to access mouse movements or other user events.  We think
Dialog Manager will help programmers (especially MIS people in corporations)
port some simple DOS programs to PM.  However, it is not nearly as rich an
environment as HyperCard.

Other changes.  Additional changes to OS/2 include the following:
   •  A new PostScript print driver.
   •  Sample driver code for programmers.
   •  The capability to change mouse drivers without reinstalling      the
operating system.



Competition/Customers
Software folder
5/23/90